Summary

EaseViews with an infinite loop animation leaked on any release path that skips view recycling (recycle pool at capacity, recycling disabled, surface teardown). CAAnimation retains its delegate, we set animation.delegate = self, and looping animations are also kept in _loopAnimations for re-adding on window re-attach — since an infinite loop never finishes, that's a permanent view → _loopAnimations → animation → view cycle that only prepareForRecycle broke. Found in a memory audit.

Two changes:

• Animations now use a proxy delegate that holds the view weakly and forwards animationDidStop:finished: (a proxy rather than nil-ing the delegate on the stored snapshot, so reapplyLoopAnimations' _pendingAnimationCount bookkeeping and onTransitionEnd events keep working).
• The all-'none' transition path called removeAllAnimations without clearing _loopAnimations, so a cancelled loop came back on the next didMoveToWindow. It now clears the saved snapshots too.

Adds an example-app reproducer (Issues → "Audit — Cancelled loop resurrects") that cancels a loop via transition={{ type: 'none' }} and uses tabs to exercise the re-attach path.

Test Plan

Verified on the iOS simulator, first against a broken-baseline build (fixes reverted, dealloc logging, shouldBeRecycled = NO to bypass the recycle pool), then the fixed build:

• Leak: unmount an EaseView with an active loop. Broken: no dealloc, ever. Fixed: dealloc fires. Non-loop EaseViews dealloc'd on both builds, so the logging itself was sound.
• Cancelled-loop resurrect: reproducer screen — spin → Cancel loop → switch tab → back. Broken: spinner resurrects. Fixed: stays stopped.
• Regressions: issue react navigation stops loop animations #42 screen still resumes loops after tab switches (reapplyLoopAnimations), and the Interrupt demo still reports both onTransitionEnd values through the proxy — "Finished" on completion, "Interrupted!" when a second toggle lands mid-animation (600 ms double-tap), then "Finished" again when the replacement animation completes.